Infrastructure appliance malfunction detection

ABSTRACT

A management system is described. The management system includes an interface coupled to a plurality of infrastructure appliances and one or more processors to monitor each of the plurality of infrastructure appliances, detect a malfunction at a first of the infrastructure appliances, and transmit a display message to the first infrastructure appliance including a message to be displayed at one or more activity light indicators at the first infrastructure appliance.

BACKGROUND

Modern data centers include thousands of racks. Each of those rackscomprise an open frame having multiple shelves, with each shelfsupporting one or more infrastructure resource appliances (e.g., server,storage, switch, etc.). For example, a shelf may include a server and/ormultiple storage drives. Additionally, each of the storage drivesinclude multiple activity light indicators visible from the front of therack. These activity light indicators typically comprise light emittingdiodes (LEDs).

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples,one or more implementations are not limited to the examples depicted inthe figures.

FIG. 1A illustrates one embodiment of a networked operating environment.

FIG. 1B illustrates one embodiment of a management system.

FIGS. 2A&2B illustrate embodiments of a rack configuration.

FIGS. 3A&3B illustrate other embodiments of a management system.

FIG. 4 is a flow diagram illustrating one embodiment of a processperformed by a management system.

FIG. 5 is a flow diagram illustrating one embodiment of a processperformed by a storage device.

DETAILED DESCRIPTION

As discussed above, data centers include many racks. Specifically, adata center may have hundreds of aisles of racks, each having manyshelves (or slots) of hardware devices. Currently, when a systemadministrator (or operator) receives an indication that a hardwareappliance has failed, the system administrator may receive an indicationon an application that specifically lists a physical address of thefailed appliance. Upon receiving the information, the operator typicallymust search for the appliance using data center coordinates (e.g., aisle27, rack 3 and slot 17). However, sometimes a problem may occur withoperators misidentifying the appliance and instead performing a repairon an incorrect appliance. For instance, a system administrator mayremove and repair an incorrect storage drive.

According to one embodiment, activity light indicators on aninfrastructure appliance are implemented to display a signal thatindicates a physical location of a failed (or failing) appliance. Insuch an embodiment, the activity light indicators may flash a sequencethat distinguishes, and is recognizable by the operator as indicating,the failed (or failing) appliance. In a further embodiment, the activitylight indicators may flash an encoded representation of the applianceserial number. In this embodiment, the operator may use a portablecomputing device to capture images and/or video of the encodedrepresentation of the appliance serial number and decode the serialnumber to enable the operator to confirm that the appliance is theactual appliance that is to be repaired.

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present disclosure. It will be apparent, however,to one skilled in the art that the present disclosure may be practicedwithout some of these specific details. In other instances, well-knownstructures and devices are shown in block diagram form to avoidobscuring the underlying principles of the present disclosure.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment.

It is contemplated that any number and type of components may be addedto and/or removed to facilitate various embodiments including adding,removing, and/or enhancing certain features. For brevity, clarity, andease of understanding, many of the standard and/or known components,such as those of a computing device, are not shown or discussed here. Itis contemplated that embodiments, as described herein, are not limitedto any particular technology, topology, system, architecture, and/orstandard and are dynamic enough to adopt and adapt to any futurechanges.

As a preliminary note, the terms “component”, “module”, “system,” andthe like as used herein are intended to refer to a computer-relatedentity, either software-executing general purpose processor, hardware,firmware and a combination thereof. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer.

By way of illustration, both an application running on a server and theserver can be a component. One or more components may reside within aprocess and/or thread of execution, and a component may be localized onone computer and/or distributed between two or more computers. Also,these components can execute from various non-transitory, computerreadable media having various data structures stored thereon. Thecomponents may communicate via local and/or remote processes such as inaccordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal).

Computer executable components can be stored, for example, onnon-transitory, computer readable media including, but not limited to,an ASIC (application specific integrated circuit), CD (compact disc),DVD (digital video disk), ROM (read only memory), floppy disk, harddisk, EEPROM (electrically erasable programmable read only memory),memory stick or any other storage device type, in accordance with theclaimed subject matter.

FIG. 1A illustrates one embodiment of a networked operating environment100 (also referred to as system 100), for implementing the variousadaptive aspects of the present disclosure. In one aspect, system 100may include a plurality of computing systems 104A-104N (may also bereferred to and shown as server system 104 or as host system 104) thatmay access one or more shared storage systems 108 via a connectionsystem 116 such as a local area network (LAN), wide area network (WAN),the Internet and others. The server systems 104 may operate as computingnodes of a master-less database cluster and may communicate with eachother via connection system 116, for example, for working collectivelyto provide data-access service to user consoles 102A-102N (may bereferred to as user 102 or client systems 102).

Server systems 104 may be computing devices (or nodes) configured toexecute applications 106A-106N (referred to as application 106 orapplications 106) over a variety of operating systems, including theUNIX® and Microsoft Windows® operating systems. Applications 106 mayutilize data services of storage system 108 to access, store, and managedata in a set of storage devices 110 that are described below in detail.

Application 106 may include a database program (for example, Cassandraand other similar database applications) that is executed in amaster-less distributed database cluster, as described below in detail.The term database node as used herein may include a stand-alone serveror a virtual machine executing an instance of the database application.

Server systems 104 generally utilize file-based access protocols whenaccessing information (in the form of files and directories) over anetwork attached storage (NAS)-based network and/or object-based storage(or object storage). Alternatively, server systems 104 may useblock-based access protocols, for example, the Small Computer SystemsInterface (SCSI) protocol encapsulated over TCP (iSCSI) and SCSIencapsulated over Fibre Channel (FCP) to access storage via a storagearea network (SAN).

Server 104A may also execute a virtual machine environment 105,according to one aspect. In the virtual machine environment 105 aphysical resource is time-shared among a plurality of independentlyoperating processor executable virtual machines (VMs). Each VM mayfunction as a self-contained platform, running its own operating system(OS) and computer executable, application software. The computerexecutable instructions running in a VM may be collectively referred toherein as “guest software”. In addition, resources available within theVM may be referred to herein as “guest resources”.

The guest software expects to operate as if it were running on adedicated computer rather than in a VM. That is, the guest softwareexpects to control various events and have access to hardware resourceson a physical computing system (may also be referred to as a hostplatform) which may be referred to herein as “host hardware resources”.The host hardware resource may include one or more processors, resourcesresident on the processors (e.g., control registers, caches and others),memory (instructions residing in memory, e.g., descriptor tables), andother resources (e.g., input/output devices, host attached storage,network attached storage or other like storage) that reside in aphysical machine or are coupled to the host platform.

The virtual execution environment 105 executes a plurality of VMs126A-126N that execute a plurality of guest OS 128A-128N (may also bereferred to as guest OS 128) to share hardware resources 134. Asdescribed above, hardware resources 134 may include CPU, memory, I/Odevices, storage or any other hardware resource.

A virtual machine monitor (VMM) 121, for example, a processor executedhypervisor layer provided by VMWare Inc., Hyper-V layer provided byMicrosoft Corporation (without derogation of any third party trademarkrights) or any other layer type, presents and manages the plurality ofguest OS 128A-128N. VMM 121 may include or interface with avirtualization layer (VIL) 132 that provides one or more virtualizedhardware resource 134 to each guest OS. For example, VIL 132 presentsphysical storage at storage devices 110 as virtual storage (for example,as a virtual hard drive (VHD)) to VMs 126A-126N. The VMs use the VHDs tostore information at storage devices 110.

In one aspect, VMM 121 is executed by server system 104A with VMs126A-126N. In another aspect, VMM 121 may be executed by an independentstand-alone computing system, often referred to as a hypervisor serveror VMM server and VMs 126A-126N are presented via another computingsystem. It is noteworthy that various vendors provide virtualizationenvironments, for example, VMware Corporation, Microsoft Corporation(without derogation of any third party trademark rights) and others. Thegeneric virtualization environment described above with respect to FIG.1A may be customized depending on the virtual environment provider.

System 100 may also include a management system 118 for managing andconfiguring various elements of system 100. Management system 118 mayinclude one or more computing systems for performing various tasksdescribed below in detail. Management system 118 may also execute orinclude a backup/restore module 138 (for brevity referred to as backupmodule 138) that executes the various process blocks of the innovativebackup technology.

In one aspect, storage system 108 is a shared storage system havingaccess to a set of mass storage devices 110 (may be referred to asstorage devices 110) within a storage subsystem 112. As an example,storage devices 110 may be a part of a storage array within the storagesub-system 112. Storage devices 110 are used by the storage system 108for storing information. The storage devices 110 may include writablestorage device media such as magnetic disks, video tape, optical, DVD,magnetic tape, non-volatile memory devices for example, self-encryptingdrives, flash memory devices and any other similar media adapted tostore information. The storage devices 110 may be organized as one ormore groups of Redundant Array of Independent (or Inexpensive) Disks(RAID). The various aspects disclosed herein are not limited to anyparticular storage device or storage device configuration.

In one aspect, to facilitate access to storage devices 110, a storageoperating system of storage system 108 “virtualizes” the storage spaceprovided by storage devices 110. The storage system 108 can present orexport data stored at storage devices 110 to server systems 104 and VMM121 as a storage volume or one or more qtree sub-volume units includingLUNs. Each storage volume (or LUN) may be configured to store data files(or data containers or data objects), scripts, word processingdocuments, executable programs, and any other type of structured orunstructured data. From the perspective of the VMS/server systems, eachvolume can appear to be a single disk drive. However, each volume canrepresent the storage space in one disk, an aggregate of some or all ofthe storage space in multiple disks, a RAID group, or any other suitableset of storage space.

It is noteworthy that the terms “disk” and “drive” as used herein isintended to mean any storage device/space and not to limit the adaptiveaspects to any particular type of storage device, for example, harddisks.

The storage system 108 may be used to store and manage information atstorage devices 110 based on a request generated by server system 104,management system 118, user 102 and/or a VM. The request may be based onfile-based access protocols, for example, the CIFS or the NFS protocol,over TCP/IP. Alternatively, the request may use block-based accessprotocols, for example, iSCSI or FCP, or object storage protocols.

As an example, in a typical mode of operation, server system 104 (or VMs126A-126N) transmits one or more input/output (I/O) commands, such as anNFS or CIFS request, over connection system 116 to the storage system108. Storage system 108 receives the request, issues one or more I/Ocommands to storage devices 110 to read or write the data on behalf ofthe server system 104, and issues an NFS or CIFS response containing therequested data over the connection system 116 to the respective serversystem 104. In one aspect, storage system 108 may also have adistributed architecture, for example, a cluster based architecture thatmay include a separate network module and storage module.

FIG. 1B shows a block diagram of management system 118 with the backupmodule 138, according to one aspect of the present disclosure. Thevarious modules of management system 118 may be implemented in onecomputing system or in a distributed environment among multiplecomputing systems. For example, the backup module 138 maybe executed bya standalone server and/or VM.

In the illustrated aspect, the management system 118 may include agraphical user interface (GUI) module 136 to generate a GUI for use by auser. In another aspect, management system 118 may present a commandline interface (CLI) to a user. The GUI may be used to receive requeststo setup backup policies 140 based on which, the backup module 138executes backup and/or restore operations.

Management system 118 may also include a communication module 142 thatimplements one or more conventional network communication protocolsand/or APIs to enable the various modules of management system 118 tocommunicate with the various computing nodes of a database cluster 130,storage system 108, VMs 126A-126N, server system 104 and clients 102.Management system 118 also includes other modules discussed in moredetail below.

According to one embodiment, storage devices 110 in storage subsystemsystem 108 are organized in a rack configuration within a data center.FIG. 2A illustrates one embodiment of a rack configuration, in whichracks (e.g., Racks 1-3) each include a plurality of storage devices 110.As shown in FIG. 2A, each storage device 110 comprises a plurality ofactivity light indicators 215. According to one embodiment, activitylight indicators 215 comprise semiconductor light sources (e.g., LEDs)that are implemented to provide a visual status of a storage device 110.In such an embodiment, each activity light indicator 215 may provide oneor more status indicators for the storage device 110. For example, oneor more activity light indicators 215 may provide a health status (e.g.,normal operation, degraded condition, or critical condition) of thestorage device 110, while other activity light indicators 215 mayprovide the status of the internal drives. Activity light indicators 215may also be used to provide other status types (e.g., power statuson/off, thermal warnings, etc.).

FIG. 3A illustrates one embodiment of management system 118 coupled tostorage device 110. As shown in FIG. 3A, in one embodiment, managementsystem 118 includes an indicator control manager 320 to control activitylight indicators 215 within each storage device 110. In this embodiment,the indicator control manager 320 communicates with each storage device110 within a storage subsystem system 108 in order to receive statusinformation from the storage device 110. Upon receiving a message from astorage device 110 indicating that the device is experiencing amalfunction that involves maintenance to be performed by an operator,the indicator control manager 320 transmits a message to the storagedevice 110 that is to be displayed using the activity light indicators215. The displayed message encoded within the activity light indicatorsmay include static or dynamic lighting configurations. For example, astatic pattern (e.g., lines, shapes, alphanumeric strings, and/or thelike) may be displayed with the activity light indicators allowing foridentification of the malfunctioning equipment. As another example, adynamic pattern that changes over time (e.g., lines, shapes,alphanumeric strings, blinking lights, and/or the like) may be used foridentification of the malfunctioning equipment.

In some embodiments, storage device 110 may be unable to receivecommunications from control manager 320. As such, control manager 320may identify one or more adjacent storage devices and transmit a messageto the one or more adjacent storage devices. While the adjacent storagedevices are not malfunctioning, the can guide the operator to themalfunctioning equipment that needs to be replaced. For example, in someembodiments, the adjacent storage devices can all be instructed todisplay an arrow using the activity light indicators pointing to thefailed (or failing) storage device.

Management system 118 also includes a baseboard management controller(BMC) interface 318 and indicator control manager 320. BMC interface 318is implemented to communicate with a BMC 378 at storage device 110 toperform management and provisioning operations (e.g., power-up, reset,update firmware, set BIOS, set Boot disk, get serial number, etc.). Inembodiments, BMC interface 318 facilitates communication betweenindicator control manager 320 and BMC 378 via an input/output controller(IOCTL) interface driver, a Representational state transfer (REST)application program interface (API), or some other system softwareproxy.

As used herein, a BMC is a specialized service processor that monitorsthe physical state of a storage device 110 (or other hardware) usingsensors and communicates with management system 118 via an independent“out-of-band” connection. In one embodiment, BMC 378 has access tohardware components within a storage device 110, and is configured todirectly modify the hardware components. As a result, BMC 378 enablesindicator control manager 320 to control the activity light indicators215 at each storage device 110. Although described herein with referenceto BMC, other embodiments may feature different types of controllersthat communicate with management system 118 via a side-band (orout-of-band) interface.

In one embodiment, indicator control manager 320 monitors the BMC 378 ateach storage device 110 in a storage sub-system 112 via BMC interface318 to determine the status of the storage device 110. In thisembodiment, indicator control manager 320 may detect malfunctioningstorage device 110 upon receiving a message from a storage device 110indicating a malfunction. Upon detecting a malfunctioning storage device110 (e.g., via a message received via a BMC 378) indicator controlmanager 320 transmits a display message to the BMC 378 that is to bedisplayed by activity light indicators 215. In one embodiment, thedisplay message includes an encoded message that is to be displayed atactivity light indicators 215. In such an embodiment, the displaymessage comprises identifier information associated with the storagedevice 110 (e.g., serial number). However, in other embodiments, thedisplay message may include an encoded representation of identifierinformation. In addition to the display message, indicator controlmanager 320 may transmit additional information to BMC 378. For example,information such as infoType, Fault Code(s), Node or Appliance SerialNumber, NodeId, Status, Error Message may be transmitted.

In response to receiving the display message, the BMC 378 causes one ormore of the activity light indicators 215 at a storage device 110 toflash in order to reveal the physical location of the storage device110, or other information types supported by this capability. In thisembodiment, the activity light indicators 215 may flash a sequence thatdistinguishes the storage device 110 from other devices in the same rackor neighboring racks. In a further embodiment, activity light indicators215 flash the encoded representation of the appliance serial number. Forexample, FIG. 2B illustrates another embodiment of the rackconfiguration, in which the activity light indicators 215 in storagedevice 110(2B) in Rack 2 display the identifier information (or anrepresentation of the identifier information) that is to be recognizedby an operator deployed to perform maintenance on storage device110(2B).

In yet a further embodiment, the operator may use a portable computingdevice to capture the image of the encoded message displayed at storagedevice 110(2B). FIG. 3B illustrates another embodiment of the managementsystem 118 also communicatively coupled to a computing device 370, aswell as storage device 110, via an interface 350. In this embodiment,interface 350 comprises a network interface that enables managementsystem 118 to be wirelessly coupled (e.g., via a wireless networkprotocol) to computing device 370. In a further embodiment, computingdevice 370 includes a mobile application 375 that also receives thedisplay message that was transmitted to the malfunctioning storagedevice 110. Additionally, the application 375 receives the serialnumber, an any additional identification information, associated withthe malfunctioning storage device 110. In a further embodiment,application 375 includes an image recognition application that scans anddecodes the encoded message displayed by the activity light indicators215, and displays information associated with storage device 110(2B). Insuch an embodiment, the image recognition application is trained to readand decode the activity light indicators 215 into human consumableinformation rendered in application 375. As a result, the operator canconfirm that the identifier information (e.g., device serial number)displayed at storage device 110(2B) matches the actual information priorto performing maintenance on the device.

FIG. 4 is a flow diagram illustrating one embodiment of a processperformed by a management system. At processing block 410, themanagement system monitors storage devices in a storage sub-system. Asdiscussed above, the management system monitors storage devices via aBMC located at each device. At processing block 420, a determination ismade as to whether a malfunctioning device has been detected. Asmentioned above, a malfunctioning storage device is detected at themanagement system by receiving a message indicating the malfunction fromthe storage device 110. Upon detecting a malfunctioning device, adisplay message is transmitted to the malfunctioning device, processingblock 430. Additionally, the display message may be transmitted to acomputing device, along with additional information identifying themalfunctioning device. Subsequently, control is returned to processingblock 410, where the management system continues to monitor the storagedevices.

FIG. 5 is a flow diagram illustrating one embodiment of a processperformed by a storage device. At processing block 510, the BMC withinthe storage device detects that there is a malfunction with the device.In accordance with various embodiments, the device may regularlycommunicate health status which can be used to identify a malfunction.In other embodiments, the BMC may periodically ping the devices. Atprocessing block 520, the BMC transmits a message to the managementsystem indicating the malfunction. At processing block 530, the BMCreceives the display message. At processing block 540, the BMC displaysthe encoded message at the activity light indicators. As discussedabove, the encoded message may be used by an operator to identify themalfunctioning device to enable the operator to perform maintenance onthe proper device. Although discussed above with reference storagedevices, other embodiments may implement activity light indicators atdifferent types of infrastructure appliances in a rack (e.g., server,switches, power devices, etc.)

Embodiments may be implemented as any or a combination of: one or moremicrochips or integrated circuits interconnected using a parent board,hardwired logic, software stored by a memory device and executed by amicroprocessor, firmware, an application specific integrated circuit(ASIC), and/or a field programmable gate array (FPGA). The term “logic”may include, by way of example, software or hardware and/or combinationsof software and hardware.

Embodiments may be provided, for example, as a computer program productwhich may include one or more machine-readable media having storedthereon machine-executable instructions that, when executed by one ormore machines such as a computer, network of computers, or otherelectronic devices, may result in the one or more machines carrying outoperations in accordance with embodiments described herein. Amachine-readable medium may include, but is not limited to, floppydiskettes, optical disks, CD-ROMs (Compact Disc-Read Only Memories), andmagneto-optical disks, ROMs, RAMs, EPROMs (Erasable Programmable ReadOnly Memories), EEPROMs (Electrically Erasable Programmable Read OnlyMemories), magnetic or optical cards, flash memory, or other type ofmedia/machine-readable medium suitable for storing machine-executableinstructions.

Moreover, embodiments may be downloaded as a computer program product,wherein the program may be transferred from a remote computer (e.g., aserver) to a requesting computer (e.g., a client) by way of one or moredata signals embodied in and/or modulated by a carrier wave or otherpropagation medium via a communication link (e.g., a modem and/ornetwork connection).

The drawings and the forgoing description give examples of embodiments.Those skilled in the art will appreciate that one or more of thedescribed elements may well be combined into a single functionalelement. Alternatively, certain elements may be split into multiplefunctional elements. Elements from one embodiment may be added toanother embodiment. For example, orders of processes described hereinmay be changed and are not limited to the manner described herein.Moreover, the actions in any flow diagram need not be implemented in theorder shown; nor do all of the acts necessarily need to be performed.Also, those acts that are not dependent on other acts may be performedin parallel with the other acts. The scope of embodiments is by no meanslimited by these specific examples. Numerous variations, whetherexplicitly given in the specification or not, such as differences instructure, dimension, and use of material, are possible. The scope ofembodiments is at least as broad as given by the following claims.

What is claimed is:
 1. A management system, comprising: an interfacecoupled to a plurality of infrastructure appliances in one or more datacenter racks, each of the plurality of infrastructure appliancescomprising a set of two or more activity light indicators; and one ormore processors to monitor the plurality of infrastructure appliancesvia the interface, the one or more processors to detect a malfunction ofat least one of the plurality of infrastructure appliances and totransmit to a first infrastructure appliance an encoded message to causeto be displayed using the activity light indicators of the firstinfrastructure appliance to provide a representation of identifierinformation associated with the infrastructure appliance experiencingthe malfunction to be decoded by an image recognition application thatcaptures one or more images of the activity light indicators of thefirst infrastructure appliance.
 2. The management system of claim 1,wherein the identifier information comprises a serial number associatedwith the first infrastructure appliance.
 3. The management system ofclaim 1, wherein the detecting the malfunction at the firstinfrastructure appliance comprises receiving a message from the firstinfrastructure appliance indicating the malfunction.
 4. The managementsystem of claim 1, wherein the image recognition application is runningon a portable computing device to confirm that the identifierinformation displayed at the first infrastructure device matchesinformation associated with the first infrastructure device.
 5. Themanagement system of claim 1, wherein the first infrastructure appliancecomprises a storage device.
 6. An infrastructure appliance, comprising:a baseboard management controller to receive an encoded message from amanagement system and to decode the encoded message to generate adisplay message; and a plurality of light emitting diodes (LEDs) coupledwith the baseboard management controller, the plurality of LEDs todisplay identifier information corresponding to a malfunctioninginfrastructure appliance based on the decoded message, the identifierinformation corresponds to infrastructure appliance to identify themalfunctioning infrastructure appliance within a data center rack,wherein the display message comprises an encoded representation ofidentifier information associated with the malfunctioning infrastructureappliance to be decoded by an image recognition application thatcaptures one or more images of the plurality of LEDs.
 7. Theinfrastructure appliance of claim 6, wherein the one or more of theplurality of LEDs flash a sequence comprising the display message. 8.The infrastructure appliance of claim 7, wherein the baseboardmanagement controller detects a malfunction at the infrastructureappliance.
 9. The infrastructure appliance of claim 8, wherein thebaseboard management controller transmits a message to the managementsystem indicating the malfunction at the infrastructure appliance. 10.The infrastructure appliance of claim 6, wherein the infrastructureappliance comprises a data storage device.
 11. A non-transitorymachine-readable medium storing instructions which, when executed by aprocessor, cause the processor to: monitor each of a plurality ofinfrastructure appliances in one or more data center racks; detect amalfunction at a first of the infrastructure appliances; and transmit anencoded message to at least one of the plurality of infrastructureappliances indicating a message to be displayed using a plurality oflight emitting diodes (LEDs) of the at least one of the plurality ofinfrastructure appliances, wherein the display message comprises arepresentation of identifier information associated with the firstinfrastructure appliance to be decoded by an image recognitionapplication that captures one or more images of the plurality of LEDs.12. The non-transitory machine-readable medium of claim 11, wherein thedisplay message comprises identifier information associated with thefirst infrastructure appliance.
 13. The non-transitory machine-readablemedium of claim 12, wherein detecting the malfunction at the firstinfrastructure appliance comprises receiving a message from the firstinfrastructure appliance indicating the malfunction.
 14. Thenon-transitory machine-readable medium of claim 11, storing instructionswhich, when executed by a processor, further cause the processor totransmit the display message to a portable computing device.
 15. Amethod to facilitate distinguishing of a malfunctioning appliance,comprising: receiving an encoded message at a baseboard managementcontroller in an infrastructure appliance from a management system,wherein the encoded message comprises identifier information associatedwith the malfunctioning appliance; and displaying a pattern with aplurality of light emitting diodes (LEDs) to identify the malfunctioningappliance within a data center rack, wherein the plurality of LEDs areactivated to provide a display message that comprises a representationof identifier information associated with the malfunctioning applianceto be decoded by an image recognition application that captures one ormore images of the plurality of LEDs.
 16. The method of claim 15,further comprising the baseboard management controller detecting amalfunction at the infrastructure appliance.
 17. The method of claim 16,further comprising the baseboard management controller transmitting amessage to the management system indicating the malfunction at theinfrastructure appliance.
 18. The method of claim 17, wherein thedisplay message comprises identifier information associated with thefirst infrastructure appliance.
 19. The method of claim 18, wherein theinfrastructure appliance comprises a data storage device.